Require Python 3.11 and adopt native typing and diagnostics - #186

Note

Medium Risk
Raising the minimum Python version is a breaking change for 3.10 users; runtime behavior is unchanged but install and CI coverage shift to 3.11–3.14 only.

Overview
Drops Python 3.10 now that it is EOL and requires Python 3.11+ (still capped below 3.15).

requires-python in pyproject.toml moves from >=3.10 to >=3.11. The GitHub Actions test matrix no longer runs on 3.10. All four uv run --script example headers under examples/ use >=3.11,<3.14.

uv.lock is regenerated for the new floor: dual-resolution markers and Python 3.10-only wheels/backports (e.g. exceptiongroup, tomli, backports-asyncio-runner, older numpy/networkx pins) are removed.

^{Reviewed by Cursor Bugbot for commit acd9f3a. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Require Python 3.11 and adopt native typing and better error diagnostics

• Raises the minimum Python from 3.10 to 3.11 in pyproject.toml, the example scripts, and the CI test matrix in test.yml
• Refactors base.py to Python 3.11 typing: ToolCallParseStatus now uses StrEnum, Message.role and Message.content become required keys via Required[...], and the module drops postponed-annotation setup
• Annotates Pydantic validators with Self in configs.py; validation logic is unchanged
• load_tokenizer and create_renderer in base.py now add exception notes naming the tokenizer or renderer before re-raising
• Adds tests covering ToolCallParseStatus wire values and Message required/optional keys
• Risk: behavioral change — Python 3.10 is now unsupported at install and runtime, and ToolCallParseStatus string conversion and JSON encoding use the member's wire value

^{Macroscope summarized cb53305.}